home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
C/C++ Users Group Library 1996 July
/
C-C++ Users Group Library July 1996.iso
/
vol_300
/
332_01
/
readme.now
< prev
next >
Wrap
Text File
|
1990-01-12
|
18KB
|
362 lines
PCCURSES v.1.4 Release Notes - 900114
===================================================
This is the release note for the fifth version of PCcurses, v.1.4.
Below this note, the release notes for v.1.0 - v.1.3 are included. Read
those first.
In PCcurses v.1.4, both portability improvements and bugfixes have
been made. The files have been changed to allow lint-free compilation
with MicroSoft 'C' v.5.1, and with Turbo 'C' v.2.0. The source should
still compile without problems on older compilers, although this has
not been verified.
The makefiles have been changed to suit both the public release and
the author, who maintains a special kind of libraries for himself. In
the case of MicroSoft 'C', changes were done in the makefile to lower
the warning level to 2 (was 3). This was to avoid ANSI warnings which
are abundant because PCcurses does not attempt to follow strict ANSI
'C' standard.
BUG FIXES FROM V.1.3 TO V.1.4:
!!!IMPORTANT CHANGE!!!
The definitions for OK and ERR in curses.h were exchanged. This was
done to be more consistent with UNIX versions. Also, it permits func-
tions like newwin() and subwin() to return 0 (=NULL) when they fail
due to memory shortage. This incompatibility with UNIX curses was
pointed out by Fred C. Smith. If you have tested success/failure by
comparisons to anything other than ERR and OK, your applications will
need to be be changed on that point. Sorry... but presumably most of
you used the symbolic constants?
(END OF IMPORTANT CHANGE)
Fred also pointed out a bug in the file update.c. The bug caused the
first character printed after 'unauthorized' screen changes (like du-
ring a shell escape, for example) to be placed at the wrong screen posi-
tion. This happened even if the normal precautions (clear / touch / re-
fresh) were taken. The problem has now been fixed.
PCcurses is currently also being used on a 68000 system with hard-
coded ESCape sequences for ANSI terminals. However, int's used by the
68000 C compiler are 32 bits. Therefore int's have been turned into
short's wherever possible in the code (otherwise all window structures
occupy twice as much space as required on the 68000). This does not
affect PC versions since normally both int's and short's are 16 bits
for PC C compilers.
At some places in the source code there are references made to the
68000 version. There are also a makefile, a curses68.c file, and a
curses68.cmd file. These are for making, low-level I/O, and linking
commands when building the 68000 version. These files are probably
useful to no-one but the author, since it is very specific for it's
special hardware environment. Still in an effort to keep all curses-
related sources in one place they are included. Note however that
PCcurses will not officially support a non-PC environment.
The file cursesio.c, which was included in the package at revision
level 1.2, and which was to be an alternative to the cursesio.asm
file, has been verified to behave incorrectly in the function
_curseskeytst(). The problem was that the value of 'cflag' does not
contain the proper data for the test that is attempted. Furthermore,
neither Turbo'C' or MicroSoft'C' allows any way to return the data
that is needed, and consequently you should not use cursesio.c. The
best solution is to simply use the ASM version. In v.1.2 and v.1.3,
the user could edit the makefile to select which version he wanted to
use. The makefiles in v.1.4 have removed this possiblity forcing the
use of the ASM file, and cursesio.c has been dropped from the distri-
bution.
A bug in the wgetstr() function caused PCcurses to echo characters
when reading a keyboard string, even if the echo had been turned off.
Thanks to Per Foreby at Lund University, Sweden, for this. Per also
reported bugs concerning the handling of characters with bit 8 set.
Their ASCII code were considered as lower than 32, so they were
erased etc. like control characters, i.e. erasing two character posi-
tions. The control character test was changed to cope with this.
The overlay() and overwrite() functions were changed so that the
overlaying window is positioned at it's 'own' coordinates inside the
underlying window (it used to be at the underlying window's [0,0]
position). There is some controversy about this - the documentation
for different curses versions say different things. I think the
choice made is the most reasonable.
The border() and wborder() functions were changed to actually draw
a border, since this seems to be the correct behaviour of these func-
tions. They used to just set the border characters to be used by
box(). These functions are not present in standard BSD UNIX curses.
The subwin() function previously did not allow the subwindow to be
as big as the original window in which it was created. This has now
been fixed. There was also the problem that the default size (set by
specifying numlines or numcols (or both) as 0 made the resulting
actual size 1 line/column too small.
There were a few spelling errors in function names, both in the
function declarations and in curses.h. This was reported by Carlos
Amaral at INESC in Portugal. Thanks! There was also an unnecessary
(but harmless) parameter in a function call at one place.
PCCURSES v.1.3 Release Notes - 881005
===================================================
This is the release note for the fourth version of PCcurses, v.1.3.
Below this note, the release notes for v.1.0, v.1.1 and v.1.2 are in-
cluded. Read those first.
The file 'border.c' is now included. It allows you to explicitely speci-
fy what characters should be used as box borders when the box() functions
are called. If the new border characters are non-0, they override the bor-
der characters specified in the box() call. In my understanding, this func-
tionality is required for AT&T UNIX sV.3 compatibility. Thanks for this
goes to Tony L. Hansen (hansen@pegasus.UUCP) for posting an article about
it on UseNet (newsgroup comp.unix.questions; his posting was not related
at all to PCcurses).
The only other difference between v.1.2 and v.1.3 is that the latter has
been changed to avoid warning diagnostics if the source files are compiled
with warning switches on (for MicroSoft this means '-W3', for Turbo'C' it
means '-w -w-pro'). Of these, the Turbo'C' warning check is clearly to be
used rather than MicroSoft, even if neither of them comes even close to a
real UNIX 'lint'. Some of the warnings in fact indicated real bugs, mostly
functions that did not return correct return values or types.
The makefiles for both MSC and TRC have been modified to produce warning
messages as part of normal compilation.
PCCURSES v.1.2 Release Notes - 881002
===================================================
This is the release note for the third version of PCcurses, v.1.2.
Below this note, the release notes for v.1.0 and v.1.1 are included. Read
those first.
The changes from v.1.1 to v.1.2 are minor. The biggest change is that there
was a bug related to limiting the cursor movement if the application tried to
move it outside the screen (something that should not be done anyway). Such
erronous application behaviour is now handled appropriately.
All modules have been changed to have a revison string in them, which makes
it easier to determine what version is linked into a program (or what library
version you have).
There is now a 'cursesio.c' file. That file does the same as 'cursesio.asm'
(i.e. it provides the interface to the lower-level system I/O routines). It
is written in 'C' and thus it is (possibly) more portable than the assembler
version (but still not so portable since it uses 8086 INT XX calls directly).
When one creates new curses libraries, one chooses whether to use the assem-
bler or the 'C' version of cursesio. The choice is made by commenting out the
appropriate dependencies for cursesio.obj, near the end of the makefiles.
There is now a 'setmode.c' file. T